Geofence-based triggers for automated data collection

ABSTRACT

Systems, methods, apparatus, and computer program products are provided for automated data collection using geofence-based triggers. In one embodiment, the location of a vehicle can be monitored by a variety of computing entities. By using the vehicle&#39;s location, it can be determined when the vehicle enters and/or exits defined geofences. After a determination that a vehicle has entered or exited a defined geofence, one or more events can be automatically triggered/initiated.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/052,287 filed Mar. 21, 2011, which claims priority to U.S. PatentApplication Ser. No. 61/316,664 filed Mar. 23, 2010, which is herebyincorporated herein in its entirety by reference.

BACKGROUND

Monitoring driver behavior, vehicle cargo, vehicle operating conditions,and vehicle environments can be very important. For example, when adriver is operating a vehicle in a representative capacity of anemployer, the driver's behavior is a direct reflection on the employer.For this and various other reasons, a solution is needed toautomatically trigger/initiate the collection of data.

BRIEF SUMMARY

In general, embodiments of the present invention provide systems,methods, apparatus, and computer program products for automated datacollection using geofence-based triggers.

In accordance with one aspect, a method for automated data collectionusing geofence-based triggers is provided. In one embodiment, the methodcomprises (1) monitoring the location of a vehicle to determine whetherthe vehicle has entered a geofenced area; and (2) after determining thatthe vehicle has entered the geofenced area, automatically starting thecollection of data while the vehicle is operated within the geofencedarea, wherein the data is selected from the group consisting of (a)image data collected via one or more imaging devices disposed on thevehicle and (b) telematics data collected via one or more datacollection devices disposed on the vehicle.

In accordance with another aspect, a method for automated datacollection using geofence-based triggers is provided. In one embodiment,the method comprises (1) monitoring the location of a vehicle todetermine whether the vehicle has exited a geofenced area; and (2) afterdetermining that the vehicle has exited the geofenced area,automatically starting the collection of data while the vehicle isoperated outside the geofenced area, wherein the data is selected fromthe group consisting of (a) image data collected via one or more imagingdevices disposed on the vehicle and (b) telematics data collected viaone or more data collection devices disposed on the vehicle.

In accordance with yet another aspect, a system comprising one or moreimaging devices and one or more data collection devices is provided. Inone embodiment, the system is configured to at least (1) monitor thelocation of a vehicle to determine whether the vehicle has entered ageofenced area; and (2) after determining that the vehicle has enteredthe geofenced area, automatically start the collection of data while thevehicle is operated within the geofenced area, wherein the data isselected from the group consisting of (a) image data collected via oneor more imaging devices disposed on the vehicle and (b) telematics datacollected via one or more data collection devices disposed on thevehicle.

In accordance with still another aspect, a system comprising one or moreimaging devices and one or more data collection devices is provided. Inone embodiment, the system is configured to at least (1) monitor thelocation of a vehicle to determine whether the vehicle has exited ageofenced area; and (2) after determining that the vehicle has exitedthe geofenced area, automatically start the collection of data while thevehicle is operated outside the geofenced area, wherein the data isselected from the group consisting of (a) image data collected via oneor more imaging devices disposed on the vehicle and (b) telematics datacollected via one or more data collection devices disposed on thevehicle.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Reference will be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 is a diagram of a system that can be used to practice variousembodiments of the present invention.

FIG. 2 is a diagram of a data collection device that may be used inassociation with certain embodiments of the present invention.

FIG. 3 is a schematic of a monitoring server in accordance with certainembodiments of the present invention.

FIG. 4 is a schematic of a portable device in accordance with certainembodiments of the present invention.

FIG. 5 is a flowchart illustrating operations and processes that can beused in accordance with various embodiments of the present invention.

DETAILED DESCRIPTION

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the inventions are shown. Indeed, theseinventions may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative” and “exemplary” are used to be examples with noindication of quality level. Like numbers refer to like elementsthroughout.

I. METHODS, APPARATUS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS

As should be appreciated, various embodiments may be implemented invarious ways, including as methods, apparatus, systems, or computerprogram products. Accordingly, various embodiments may take the form ofan entirely hardware embodiment or an embodiment in which a processor isprogrammed to perform certain steps. Furthermore, variousimplementations may take the form of a computer program product on acomputer-readable storage medium having computer-readable programinstructions embodied in the storage medium. Any suitablecomputer-readable storage medium may be utilized including hard disks,CD-ROMs, optical storage devices, or magnetic storage devices.

Various embodiments are described below with reference to block diagramsand flowchart illustrations of methods, apparatus, systems, and computerprogram products. It should be understood that each block of the blockdiagrams and flowchart illustrations, respectively, may be implementedin part by computer program instructions, e.g., as logical steps oroperations executing on a processor in a computing system. Thesecomputer program instructions may be loaded onto a computer, such as aspecial purpose computer or other programmable data processing apparatusto produce a specifically-configured machine, such that the instructionswhich execute on the computer or other programmable data processingapparatus implement the functions specified in the flowchart block orblocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the functionality specified in theflowchart block or blocks. The computer program instructions may also beloaded onto a computer or other programmable data processing apparatusto cause a series of operational steps to be performed on the computeror other programmable apparatus to produce a computer-implementedprocess such that the instructions that execute on the computer or otherprogrammable apparatus provide operations for implementing the functionsspecified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport various combinations for performing the specified functions,combinations of operations for performing the specified functions andprogram instructions for performing the specified functions. It shouldalso be understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions oroperations, or combinations of special purpose hardware and computerinstructions.

II. EXEMPLARY SYSTEM ARCHITECTURE

FIG. 1 provides an illustration of a system that can be used inconjunction with various embodiments of the present invention. As shownin FIG. 1, the system may include one or more vehicles 100, one or moreportable devices 105, one or more monitoring servers 110, one or moreGlobal Positioning System (GPS) satellites 115, one or more locationsensors 120, one or more telematics sensors 125, one or more datacollection devices 130, one or more networks 140, one or more imagingdevices 135, and/or the like. Each of the components of the system maybe in electronic communication with, for example, one another over thesame or different wireless or wired networks including, for example, awired or wireless Personal Area Network (PAN), Local Area Network (LAN),Metropolitan Area Network (MAN), Wide Area Network (WAN), or the like.Additionally, while FIG. 1 illustrates certain system entities asseparate, standalone entities, the various embodiments are not limitedto this particular architecture.

a. Exemplary Vehicle

In various embodiments, the vehicle 100 (such as a delivery vehicle) mayinclude one or more location sensors 120, one or more telematics sensors125, one or more data collection devices 130, one or more imagingdevices 135, and/or the like.

i. Exemplary Data Collection Device

Reference is now made to FIG. 2, which provides a block diagram of anexemplary data collection device 130. The data collection device 130 maycollect location and telematics sensor data and transmit the data to theportable device 105 and/or the monitoring server 110 via one of severalcommunication methods.

In one embodiment, the data collection device 130 may include, beassociated with, or be in communication with one or more processors 200,one or more location-determining devices or one or more location sensors120 (e.g., Global Navigation Satellite System (GNSS) sensors), one ormore telematics sensors 125, one or more real-time clocks 215, a J-Busprotocol architecture, one or more electronic control modules (ECM) 245,one or more communication ports 230 for receiving data from varioussensors (e.g., via a CAN-bus), one or more communication ports 205 fortransmitting data, one or more radio frequency identification (RFID)tags 250, one or more power sources 220, one or more data radios 235 forcommunication with a variety of communication networks, one or morememory modules 210, and one or more programmable logic controllers (PLC)225. It should be noted that many of these components may be located inthe vehicle 100 but external to the data collection device 130.

In one embodiment, the one or more location sensors 120 may be one ofseveral components in communication with or available to the datacollection device 130. Moreover, the one or more location sensors 120may be compatible with a Low Earth Orbit (LEO) satellite system or aDepartment of Defense (DOD) satellite system. Alternatively,triangulation may be used in connection with a device associated with aparticular vehicle and/or the vehicle's driver and with variouscommunication points (e.g., cellular towers or Wi-Fi access points)positioned at various locations throughout a geographic area todetermine the location of the vehicle 100 and/or its driver. The one ormore location sensors 120 may be used to receive latitude, longitude,altitude, geocode, course, position, time, and/or speed data (e.g.,location data). The one or more location sensors 120 may alsocommunicate with the monitoring server 110, the data collection device130, and/or a similar network entity.

As indicated, in addition to the one or more location sensors 120, thedata collection device 130 may include or be associated with one or moretelematics sensors 125. For example, the telematics sensors 125 mayinclude vehicle sensors, such as engine, fuel, odometer, tire pressure,location, weight, door, and speed sensors. The telematics data mayinclude, but is not limited to, vehicle speed data, RPM data, tirepressure data, oil pressure data, seat belt usage data, mileage data,fuel data, idle data, and/or the like. The telematics sensors 125 mayinclude environmental sensors, such as air quality sensors, temperaturesensors, and/or the like. Thus, the telematics data may also includecarbon monoxide (CO), nitrogen oxides (NOx), sulfur oxides (SOx), ozone(O₃), hydrogen sulfide (H₂S) and/or ammonium (NH₄) data and/ormeteorological data.

In one embodiment, the ECM 245 may be one of several components incommunication with or available to the data collection device 130. TheECM 245, which may be a scalable and subservient device to the datacollection device 130, may have data processing capability to decode andstore analog and digital inputs from vehicle systems and sensors. TheECM 245 may further have data processing capability to collect andpresent vehicle data to the J-Bus (which may allow transmission to thedata collection device 130), and output standard vehicle diagnosticcodes when received from a vehicle's J-Bus-compatible on-boardcontrollers 240 or sensors.

As indicated, a communication port 230 may be one of several componentsavailable in the data collection device 130. Embodiments of thecommunication port 230 may include an Infrared Data Association (IrDA)communication port, a data radio, and/or a serial port. Thecommunication port 230 may receive instructions for the data collectiondevice 130. These instructions may be specific to the vehicle 100 inwhich the data collection device 130 is installed, specific to thegeographical area in which the vehicle 100 will be traveling, orspecific to the function the vehicle 100 serves within the fleet. In oneembodiment, the data radio 235 may be configured to communicate with awireless wide area network (WWAN), wireless local area network (WLAN),or wireless personal area network (WPAN), or any combination thereof.For example, the data radio 235 may communicate via various wirelessprotocols, such as 802.11, general packet radio service (GPRS),Universal Mobile Telecommunications System (UMTS), Code DivisionMultiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access(WCDMA), Time Division-Synchronous Code Division Multiple Access(TD-SCDMA), Long Term Evolution (LTE), Evolved Universal TerrestrialRadio Access Network (E-UTRAN), IEEE 802.11 (Wi-Fi), 802.16 (WiMAX),ultra wideband (UWB), infrared (IR) protocols, Bluetooth protocols,wireless universal serial bus (USB) protocols, and/or any other wirelessprotocol. Via these communication standards and protocols, the datacollection device 130 can communicate with various other entities.

In one embodiment, one or more RFID tags 250 may be one of severalcomponents available for use with the data collection device 130. Oneembodiment of the one or more RFID tags 250 may include active RFIDtags, each of which may comprise at least one of the following: (1) aninternal clock; (2) a memory; (3) a microprocessor; and (4) at least oneinput interface for connecting with sensors located in the vehicle 100or the data collection device 130. Another embodiment of the RFID tags250 may be passive RFID tags.

ii. Exemplary Imaging Devices

The vehicle 100 may also include one or more imaging devices 135disposed therein. For example, imaging devices 135 may be disposed onthe vehicle 100 facing out toward the front, rear, and/or sides of thevehicle 100. Similarly, imaging devices 135 may be disposed on thevehicle 100 facing in toward the driver, passengers, or cargo in thevehicle 100.

In one embodiment, the imaging devices 135 may be analog or digitalcameras (or video cameras or combinations thereof) for capturing images(e.g., image data). For example, the imaging devices 135 may be cameraswith wide angle lenses and/or cameras with narrow angle lenses. In oneembodiment, the imaging devices 135 may be dual-view imaging devices 135that simultaneously record video inside and outside of the vehicle 100.The imaging devices 135 may be configured to continuously record imagesand/or video. Similarly, the imaging devices 135 may be configured toautomatically record and stop recording image data upon the occurrenceof certain specified events, such as the entering and/or exiting of ageofenced area.

In one embodiment, the imaging devices 135 may include one or moreprocessors, one or more temporary memory storage areas, and/or one ormore permanent memory storage areas. For instance, the imaging devices135 can capture (and timestamp) images (e.g., image data) and store themtemporarily in the temporary memory storage areas or permanently withinthe imaging devices 135. In one embodiment, the imaging devices 135 mayalso be connected to (or include) a network interface for communicatingwith various entities. As indicated above, this communication may be viathe same or different wired or wireless networks using a variety ofwired or wireless transmission protocols. For example, using suchprotocols, the imaging devices 135 may communicate with (e.g., receiveinstructions from and transmit image data to) the portable device 105,the monitoring server 110, and/or the data collection device 130.

b. Exemplary Monitoring Server

FIG. 3 provides a schematic of a monitoring server 110 according to oneembodiment of the present invention. In general, the term “server” mayrefer to, for example, any computer, computing device, mobile phone,desktop, notebook or laptop, distributed system, server, blade, gateway,switch, processing device, or combination of processing devices adaptedto perform the functions described herein. As will be understood fromthis figure, in one embodiment, the monitoring server 110 may include aprocessor 305 that communicates with other elements within themonitoring server 110 via a system interface or bus 361. The processor305 may be embodied in a number of different ways. For example, theprocessor 305 may be embodied as one or more processing elements, one ormore microprocessors with accompanying digital signal processors, one ormore processors without an accompanying digital signal processors, oneor more coprocessors, one or more multi-core processors, one or morecontrollers, and/or various other processing devices includingintegrated circuits such as, for example, an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), ahardware accelerator, or the like.

In an exemplary embodiment, the processor 305 may be configured toexecute instructions stored in the device memory or otherwise accessibleto the processor 305. As such, whether configured by hardware orsoftware methods, or by a combination thereof, the processor 305 mayrepresent an entity capable of performing operations according toembodiments of the present invention when configured accordingly. Adisplay device/input device 364 for receiving and displaying data mayalso be included in or associated with the monitoring server 110. Thedisplay device/input device 364 may be, for example, a keyboard orpointing device that is used in combination with a monitor. Themonitoring server 110 may further include transitory and non-transitorymemory 363, which may include both random access memory (RAM) 367 andread only memory (ROM) 365. The monitoring server's ROM 365 may be usedto store a basic input/output system (BIOS) 326 containing the basicroutines that help to transfer information to the different elementswithin the monitoring server 110.

In addition, in one embodiment, the monitoring server 110 may include atleast one storage device 368, such as a hard disk drive, a CD drive, aDVD drive, and/or an optical disk drive for storing information onvarious computer-readable media. The storage device(s) 368 and itsassociated computer-readable media may provide nonvolatile storage. Thecomputer-readable media described above could be replaced by any othertype of computer-readable media, such as embedded or removablemultimedia memory cards (MMCs), secure digital (SD) memory cards, MemorySticks, electrically erasable programmable read-only memory (EEPROM),flash memory, hard disk, or the like. Additionally, each of thesestorage devices 368 may be connected to the system bus 361 by anappropriate interface.

Furthermore, a number of program modules may be stored by the variousstorage devices 368 and/or within RAM 367. Such program modules mayinclude an operating system 380, a collection module 370, a locationmodule 360, and a trigger module 350. As discussed in greater detailbelow, these modules may control certain aspects of the operation of themonitoring server 110 with the assistance of the processor 305 andoperating system 380—although their functionality need not bemodularized. In addition to the program modules, the monitoring server110 may store or be in communication with one or more databases, such asdatabase 340.

Also located within or associated with the monitoring server 110, in oneembodiment, is a network interface 374 for interfacing with variouscomputing entities. This communication may be via the same or differentwired or wireless networks (or a combination of wired and wirelessnetworks), as discussed above. For instance, the communication may beexecuted using a wired data transmission protocol, such as fiberdistributed data interface (FDDI), digital subscriber line (DSL),Ethernet, asynchronous transfer mode (ATM), frame relay, data over cableservice interface specification (DOCSIS), or any other wiredtransmission protocol. Similarly, the monitoring server 110 may beconfigured to communicate via wireless external communication networksusing any of a variety of protocols, such as 802.11, GPRS, UMTS,CDMA2000, WCDMA, TD-SCDMA, LTE, E-UTRAN, Wi-Fi, WiMAX, UWB, and/or anyother wireless protocol.

It will be appreciated that one or more of the monitoring server's 110components may be located remotely from other monitoring server 110components. Furthermore, one or more of the components may be combinedand additional components performing functions described herein may beincluded in the monitoring server 110.

c. Exemplary Portable Device

With respect to the portable device 105, FIG. 4 provides an illustrativeschematic representative of a portable device 105 that can be used inconjunction with the embodiments of the present invention (e.g., aportable device 105 carried by a delivery driver). As shown in FIG. 4,the portable device 105 can include an antenna 412, a transmitter 404, areceiver 406, and a processing device 408, e.g., a processor,controller, or the like, that provides signals to and receives signalsfrom the transmitter 404 and receiver 406, respectively.

The signals provided to and received from the transmitter 404 and thereceiver 406, respectively, may include signaling information inaccordance with an air interface standard of applicable wireless (orwired) systems. In this regard, the portable device 105 may be capableof operating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, theportable device 105 may operate in accordance with any of a number ofsecond-generation (2G) communication protocols, third-generation (3G)communication protocols, and/or the like. Further, for example, theportable device 105 may operate in accordance with any of a number ofdifferent wireless networking techniques, such as GPRS, UMTS, CDMA2000,WCDMA, TD-SCDMA, LTE, E-UTRAN, Wi-Fi, WiMAX, UWB, and/or any otherwireless protocol. Via these communication standards and protocols, theportable device 105 can communicate with the monitoring server 110and/or various other entities.

The portable device 105 may also comprise a user interface (that caninclude a display 416 coupled to a processing device 408) and/or a userinput interface (coupled to the processing device 408). The user inputinterface can comprise any of a number of devices allowing the portabledevice 105 to receive data, such as a keypad 418, a touch display (notshown), barcode reader (not shown), RFID tag reader (not shown), orother input device. In embodiments including a keypad 418, the keypad418 can include the conventional numeric (0-9) and related keys (#, *),and other keys used for operating the portable device 105 and mayinclude a full set of alphabetic keys or set of keys that may beactivated to provide a full set of alphanumeric keys. In addition toproviding input, the user input interface can be used, for example, toactivate or deactivate certain functions, such as screen savers and/orsleep modes. Although not shown, the portable device 105 may alsoinclude a battery, such as a vibrating battery pack, for powering thevarious circuits that are required to operate the portable device 105,as well as optionally providing mechanical vibration as a detectableoutput.

The portable device 105 can also include volatile memory 422 and/ornon-volatile memory 424, which can be embedded and/or may be removable.For example, the non-volatile memory may be embedded or removable MMCs,SD memory cards, Memory Sticks, EEPROM, flash memory, hard disk, or thelike. The memory can store any of a number of pieces or amount ofinformation and data used by the portable device 105 to implement thefunctions of the portable device 105. The memory can also store content,such as computer program code for an application and/or other computerprograms.

The portable device 105 may also include a GPS module adapted toacquire, for example, latitude, longitude, altitude, geocode, course,speed, universal time (UTC), date, and/or telematics information/data.In one embodiment, the GPS module acquires data, sometimes known asephemeris data, by identifying the number of satellites in view and therelative positions of those satellites. In addition, data regarding, forexample, heading and estimated time of arrival (ETA) can also becaptured, which enhances the determination of the position of the GPSmodule.

III. EXEMPLARY SYSTEM OPERATION

Reference will now be made to FIG. 5. FIG. 5 illustrates operations andprocesses that can be performed to trigger geo-fence based events.

a. Defined Geographic Areas

In one embodiment, as shown in FIG. 5, the process may be begin at Block500 with a computing entity (e.g., via a user operating a computingentity) defining one or more geographic areas. In one embodiment, thegeographic areas may correspond to areas within which one or moreparcels may be picked up and/or delivered (e.g., a delivery route). Eachgeographic area may, for example, represent an area in which a singledriver may be capable of handling all parcel pick-ups and deliverieswithin a given delivery cycle (e.g., an eight-hour day). In oneembodiment, the geographic areas may correspond to bus routes or taxisroutes (e.g., driven by school bus, transit bus drivers, and/or taxisdrivers). In one embodiment, the geographic areas may be defined basedon predefined size requirements (e.g., a new geographic area may occurevery 100,000 square feet). Alternatively, the geographic areas may bedefined based on zoning classifications associated with differentgeographic areas (e.g., an office park may make up an individualgeographic area).

In another embodiment, one or more of the geographic areas may bedefined based on the existence of one or more housing subdivisions,office parks, and/or the like. For example, each housing subdivision, ora combination of two or more abutting housing subdivisions, may make upa defined geographic area. This may depend, for example, on the squarefootage of each subdivision and/or the number of houses within eachsubdivision.

In yet another alternative embodiment, one or more of the geographicareas may be defined based on the average number of potential stops(e.g., delivery stops, stoplights, and/or stop signs) and/or thefrequency of stops within certain geographic areas. This may bedetermined, for example, based on information gathered regarding pastpick-ups and deliveries within that geographic area.

According to various embodiments of the present invention, a geographicarea may overlap or reside wholly within another geographic area.Geographic areas may, for example, be as small as a singledelivery/pick-up stop or a suite within a commercial building, or aslarge as an entire town, city, county, or state. According to variousembodiments, the geographic areas need not be continuous. In otherwords, a geographic area may specifically exclude an area that wouldotherwise fall within the geographic area (e.g., such that thegeographic area forms a donut or similar shape around the excludedarea).

The geographic areas may be defined based on any number and combinationof factors including, but not limited to, those described above. Theforegoing examples are therefore provided for exemplary purposes onlyand should not be taken in any way as limiting embodiments of thepresent invention to the examples provided.

b. Defined Geofences

In one embodiment, once the geographic areas have been defined, acomputing entity (e.g., via a user operating a computing entity) maydefine one or more geofences (Block 505), such as defining a geofencearound a geographic area. The geofences may be defined to surround adefined geographic area, a neighborhood, a parcel delivery route, a zipcode, a school zone, a city, and/or the like. The geofence may bedefined, for example, by the latitude and longitude coordinatesassociated with various points along the perimeter of the geographicarea. Alternatively, the geofence may be defined based on latitude andlongitude coordinates of the center, as well as the radius, of thegeographic area. The geographic area, and therefore the geofence, may beany shape including, but not limited to, a circle, square, rectangle, anirregular shape, and/or the like. Moreover, the geofenced areas need notbe the same shape or size. Accordingly, any combination of shapes andsizes may be used in accordance with embodiments of the presentinvention. Similarly, a geofence may overlap or reside wholly withinanother geofence. Geofences may, for example, be as small as a singledelivery/pick-up stop or a suite within a commercial building, or aslarge as an entire city, county, or state.

In one embodiment, once at least one geofence has been defined, thecoordinates (or similar means for defining the geofenced areas) may bestored in a database associated with, for example, the data collectiondevice 130, portable device 105, and/or monitoring server 110. Thus, asthe vehicle enters and exits the defined one or more defined geofences,a computing entity (the data collection device 130, portable device 105,and/or monitoring server 110) can monitor the location of the vehicle100 and trigger/initiate certain events based on the vehicle's 100location.

c. Geofence-Based Triggers

In one embodiment, after the one or more geofences have been defined,the location of the vehicle 100 can be monitored (Block 510). Inparticular, the location of the vehicle can be monitored by any of avariety of computing entities (e.g., via a location module 360),including the data collection device 130, the portable device 105,and/or the monitoring server 110. For example, as noted above, thevehicle's 100 location at a particular time may be determined with theaid of one or more location-determining devices and/or one or morelocation sensors 120 (e.g., GNSS sensors). By using the vehicle's 100location, a computing entity (data collection device 130, portabledevice 105, or monitoring server 110) can determine, for example, whenthe vehicle 100 enters and/or exits a defined geofence (Block 515).

In one embodiment, as indicated in Block 520, in response to (e.g.,after) a determination that a vehicle 100 has entered or exited adefined geofence, a computing entity (e.g., the data collection device130, portable device 105, or monitoring server 110) can automaticallytrigger/initiate one or more events. In various embodiments, thisfunctionality can provide for the automatic collection of data (e.g.,image data and telematics data) as vehicles 100 enter and exit definedgeofences.

In one embodiment, after a computing entity (e.g., the data collectiondevice 130, portable device 105, or monitoring server 110) determinesthat a vehicle 100 has entered a defined geofence, the computing entitycan transmit/initiate a communication that causes the vehicle's 100 oneor more (i) imaging devices 135 to automatically turn on and/or beginrecording image data and/or (ii) data collection devices 130 toautomatically turn on and/or begin collecting telematics data. Forexample, the data collection device 130 can determine that the vehicle100 has entered a defined geofence and automatically transmit/initiate acommunication (i) to the one or more imaging devices 135 that causesthem to automatically turn on and/or begin recording image data and/or(ii) that causes the data collection device 130 to begin collectingtelematics data. In another example, the portable device 105 (and/ormonitoring server 110) can determine that the vehicle 100 has entered adefined geofence and transmit/initiate a communication (i) to the one ormore imaging devices 135 that causes them to automatically turn onand/or begin recording image data and/or (ii) to the one or more datacollection devices 130 that causes them to automatically turn on and/orbegin collecting telematics data. Similarly, after a computing entity(e.g., the data collection device 130, portable device 105, ormonitoring server 110) determines that the vehicle 100 has exited thedefined geofence, the computing entity can transmit/initiate acommunication that causes the vehicle's 100 one or more (i) imagingdevices 135 to automatically turn off and/or stop recording image dataand/or (ii) data collection devices 130 to automatically turn off and/orstop collecting telematics data.

Alternatively, in one embodiment, after a computing entity (e.g., thedata collection device 130, portable device 105, or monitoring server110) determines that a vehicle 100 has exited a defined geofence, thecomputing entity can transmit/initiate a communication that causes thevehicle's 100 one or more (i) imaging devices 135 to automatically turnon and/or begin recording image data (e.g., via a trigger module 350)and/or (ii) data collection devices 130 to automatically turn on and/orbegin collecting telematics data (e.g., via a trigger module 350).Similarly, after a computing entity (e.g., the data collection device130, portable device 105, or monitoring server 110) determines that thevehicle 100 has entered the defined geofence, the computing entity cantransmit/initiate a communication that causes the vehicle's 100 one ormore (i) imaging devices 135 to automatically turn off and/or stoprecording image data and/or (ii) data collection devices 130 toautomatically turn off and/or stop collecting telematics data (e.g., asdescribed previously).

In one embodiment, the one or more (i) imaging devices 135 may beconfigured to continuously record image data and/or (ii) data collectiondevices 130 may be configured to continuously collect telematics datawhen the vehicle 100 is in use. In this particular embodiment, after acomputing entity (e.g., the data collection device 130, portable device105, or monitoring server 110) determines that the vehicle 100 hasexited a defined geofence, the computing entity can transmit/initiate acommunication that causes the vehicle's 100 one or more (i) imagingdevices 135 to automatically transmit (or store) image data beingrecorded to a computing entity and/or (ii) data collection devices 130to automatically transmit (or store) telematics data being collected toa computing entity (e.g., as described previously). Similarly, after acomputing entity (e.g., the data collection device 130, portable device105, or monitoring server 110) determines that the vehicle 100 hasentered the defined geofence, the computing entity can transmit/initiatea communication that causes the vehicle's 100 one or more (i) imagingdevices 135 to automatically stop transmitting (or storing) image databeing recorded to a computing entity and/or (ii) data collection devices130 to automatically stop transmitting (or storing) telematics databeing collected to a computing entity (e.g., as described previously).

Alternatively, in one embodiment, the one or more (i) imaging devices135 may be configured to continuously record image data and/or (ii) datacollection devices 130 may be configured to continuously collecttelematics data when the vehicle 100 is in use. In a particularembodiment, after a computing entity (e.g., the data collection device130, portable device 105, or monitoring server 110) determines that thevehicle 100 has entered a defined geofence, the computing entity cantransmit/initiate a communication that causes the vehicle's 100 one ormore (i) imaging devices 135 to automatically transmit (or store) imagedata being recorded to a computing entity and/or (ii) data collectiondevices 130 to automatically transmit (or store) telematics data beingcollected to a computing entity (e.g., as described previously).Similarly, after a computing entity (e.g., the data collection device130, portable device 105, or monitoring server 110) determines that thevehicle 100 has exited the defined geofence, the computing entity cantransmit/initiate a communication that causes the vehicle's 100 one ormore (i) imaging devices 135 to automatically stop transmitting (orstoring) image data being recorded to a computing entity and/or (ii)data collection devices 130 to automatically stop transmitting (orstoring) telematics data being collected to a computing entity (e.g., asdescribed previously).

In one embodiment, the one or more (i) imaging devices 135 may beconfigured to continuously record image data and/or (ii) data collectiondevices 130 may be configured to continuously collect telematics datawhen the vehicle 100 is in use. In a particular embodiment, after acomputing entity (e.g., the data collection device 130, portable device105, or monitoring server 110) determines that the vehicle 100 hasexited a defined geofence, the computing entity can transmit/initiate acommunication that causes the vehicle's 100 one or more (i) imagingdevices 135 to automatically begin storing image data being recorded toone or more memory storage areas (e.g., via a collection module 370)and/or (ii) data collection devices 130 to automatically begin storingtelematics data being collected to one or more memory storage areas(e.g., as described previously). Similarly, after a computing entity(e.g., the data collection device 130, portable device 105, ormonitoring server 110) determines that the vehicle 100 has entered thedefined geofence, the computing entity can transmit/initiate acommunication that causes the vehicle's 100 one or more (i) imagingdevices 135 to automatically stop storing image data being recorded toone or more memory storage areas and/or (ii) data collection devices 130to automatically stop storing telematics data being collected to one ormore memory storage areas (e.g., as described previously).

Alternatively, in one embodiment, the one or more (i) imaging devices135 may be configured to continuously record image data and/or (ii) datacollection devices 130 may be configured to continuously collecttelematics data when the vehicle 100 is in use. In a particularembodiment, after a computing entity (e.g., the data collection device130, portable device 105, or monitoring server 110) determines that thevehicle 100 has entered a defined geofence, the computing entity cantransmit/initiate a communication that causes the vehicle's 100 one ormore (i) imaging devices 135 to automatically begin storing image databeing recorded to one or more memory storage areas and/or (ii) datacollection devices 130 to automatically begin storing telematics databeing collected to one or more memory storage areas (e.g., as describedpreviously). Similarly, after a computing entity (e.g., the datacollection device 130, portable device 105, or monitoring server 110)determines that the vehicle 100 has exited the defined geofence, thecomputing entity can transmit/initiate a communication that causes thevehicle's 100 one or more (i) imaging devices 135 to automatically stopstoring image data being recorded to one or more memory storage areasand/or (ii) data collection devices 130 to automatically stop storingtelematics data being collected to one or more memory storage areas(e.g., as described previously). As will be recognized, a variety ofapproaches and techniques may be used to trigger/initiate the automatedcollection of data, such as triggers based on harsh braking, turning anengine one or off, and/or the like. Accordingly, the foregoing examplesare provided for illustrative purposes only and should not be taken inany way as limiting embodiments of the present invention to the examplesprovided.

IV. CONCLUSION

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseembodiments of the invention pertain having the benefit of the teachingspresented in the foregoing descriptions and the associated drawings.Therefore, it is to be understood that the embodiments of the inventionare not to be limited to the specific embodiments disclosed and thatmodifications and other embodiments are intended to be included withinthe scope of the appended claims. Although specific terms are employedherein, they are used in a generic and descriptive sense only and notfor purposes of limitation.

1. A method for the automated collection of data comprising: monitoring,via one or more processors, the location of a vehicle to determinewhether the vehicle has entered a geofenced area; and after determiningthat the vehicle has entered the geofenced area, automatically starting,via the one or more processors, the collection of data while the vehicleis operated within the geofenced area, wherein the data is selected fromthe group consisting of (a) image data collected via one or more imagingdevices disposed on the vehicle and (b) telematics data collected viaone or more data collection devices disposed on the vehicle.
 2. Themethod of claim 1 further comprising: monitoring the location of thevehicle to determine whether the vehicle has exited the geofenced area;and after determining that the vehicle has exited the geofenced area,automatically stopping the collection of the data while the vehicle isoperated outside the geofenced area.
 3. The method of claim 1, whereinthe data collected comprises image data collected via one or moreimaging devices disposed on the vehicle.
 4. The method of claim 3further comprising transmitting at least a portion of the image datafrom the one or more imaging devices to a computing entity.
 5. Themethod of claim 1, wherein the data collected comprises telematics datacollected via one or more data collection devices disposed on thevehicle.
 6. The method of claim 5 further comprising transmitting atleast a portion of the telematics data from the one or more datacollection devices disposed on the vehicle to a computing entity.
 7. Amethod for the automated collection of data comprising: monitoring, viaone or more processors, the location of a vehicle to determine whetherthe vehicle has exited a geofenced area; and after determining that thevehicle has exited the geofenced area, automatically starting, via theone or more processors, the collection of data while the vehicle isoperated outside the geofenced area, wherein the data is selected fromthe group consisting of (a) image data collected via one or more imagingdevices disposed on the vehicle and (b) telematics data collected viaone or more data collection devices disposed on the vehicle.
 8. Themethod of claim 7 further comprising: monitoring the location of thevehicle to determine whether the vehicle has entered the geofenced area;and after determining that the vehicle has entered the geofenced area,automatically stopping the collection of the data while the vehicle isoperated within the geofenced area.
 9. The method of claim 7, whereinthe data collected comprises image data collected via one or moreimaging devices disposed on the vehicle.
 10. The method of claim 9further comprising transmitting at least a portion of the image datafrom the one or more imaging devices to a computing entity.
 11. Themethod of claim 7, wherein the data collected comprises telematics datacollected via one or more data collection devices disposed on thevehicle.
 12. The method of claim 11 further comprising transmitting atleast a portion of the telematics data from the one or more datacollection devices disposed on the vehicle to a computing entity.
 13. Asystem comprising one or more imaging devices and one or more datacollection devices, the system configured to: monitor the location of avehicle to determine whether the vehicle has entered a geofenced area;and after determining that the vehicle has entered the geofenced area,automatically start the collection of data while the vehicle is operatedwithin the geofenced area, wherein the data is selected from the groupconsisting of (a) image data collected via one or more imaging devicesdisposed on the vehicle and (b) telematics data collected via one ormore data collection devices disposed on the vehicle.
 14. The system ofclaim 13 further configured to: monitor the location of the vehicle todetermine whether the vehicle has exited the geofenced area; and afterdetermining that the vehicle has exited the geofenced area,automatically stop the collection of the data while the vehicle isoperated outside the geofenced area.
 15. The system of claim 13, whereinthe data collected comprises image data collected via the one or moreimaging devices disposed on the vehicle.
 16. The system of claim 15further configured to transmit at least a portion of the image data fromthe one or more imaging devices to a computing entity.
 17. The system ofclaim 13, wherein the data collected comprises telematics data collectedvia the one or more data collection devices disposed on the vehicle. 18.The system of claim 17 further configured to transmit at least a portionof the telematics data from the one or more data collection devicesdisposed on the vehicle to a computing entity.
 19. A system comprisingone or more imaging devices and one or more data collection devices, thesystem configured to: monitor the location of a vehicle to determinewhether the vehicle has exited a geofenced area; and after determiningthat the vehicle has exited the geofenced area, automatically start thecollection of data while the vehicle is operated outside the geofencedarea, wherein the data is selected from the group consisting of (a)image data collected via one or more imaging devices disposed on thevehicle and (b) telematics data collected via one or more datacollection devices disposed on the vehicle.
 20. The system of claim 19further configured to: monitor the location of the vehicle to determinewhether the vehicle has entered the geofenced area; and afterdetermining that the vehicle has entered the geofenced area,automatically stop the collection of the data while the vehicle isoperated within the geofenced area.
 21. The system of claim 19, whereinthe data collected comprises image data collected via the one or moreimaging devices disposed on the vehicle.
 22. The system of claim 21further configured to transmit at least a portion of the image data fromthe one or more imaging devices to a computing entity.
 23. The system ofclaim 19, wherein the data collected comprises telematics data collectedvia the one or more data collection devices disposed on the vehicle. 24.The system of claim 23 further configured to transmit at least a portionof the telematics data from the one or more data collection devicesdisposed on the vehicle to a computing entity.